An architectural model for electronic services

In addition to producing a pervasive standard and atechnology framework, the Web Service initiative hasprompted businesses to re-examine their service deliverychannels. Back-end systems are already in place tocapture business knowledge and manage operationalstrategies and procedures. Web Services enable access tosuch systems, as well as basic orchestration. Theinfrastructure is in place to recreate the business-levelnotion of an electronic service. However, the gap betweentechnology-oriented and business-oriented models forservices is still considerable.In this paper, we outline a model for electronic servicesas defined by the FRESCO project. The model constitutesan architectural blueprint of the technical and businessinfrastructure for an electronic service. The focus is onthe provisional aspects of electronic services

Metamodel-based model conformance and multiview consistency checking

Model-driven development, using languages such as UML and BON, often makes use of multiple diagrams (e.g., class and sequence diagrams) when modeling systems. These diagrams, presenting different views of a system of interest, may be inconsistent. A metamodel provides a unifying framework in which to ensure and check consistency, while at the same time providing the means to distinguish between valid and invalid models, that is, conformance. Two formal specifications of the metamodel for an object-oriented modeling language are presented, and it is shown how to use these specifications for model conformance and multiview consistency checking. Comparisons are made in terms of completeness and the level of automation each provide for checking multiview consistency and model conformance. The lessons learned from applying formal techniques to the problems of metamodeling, model conformance, and multiview consistency checking are summarized